Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1cf12d485fe63d1184cfd7c0111b58bfaaa5bb88be8326864a37cd1bf30b9371

Tx prefix hash: 962a75c524de97c2fb106c6490eb40c582554e2574d0c4264be03f9f2ad2cbc3
Tx public key: 4d49b6f9cd4eec9b9be60a210a4a987ffc2bdfde374a1974befbbf6b516fce84
Timestamp: 1702652651 Timestamp [UCT]: 2023-12-15 15:04:11 Age [y:d:h:m:s]: 01:330:02:33:35
Block: 913736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494787 RingCT/type: yes/0
Extra: 014d49b6f9cd4eec9b9be60a210a4a987ffc2bdfde374a1974befbbf6b516fce8402110000000c33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1d22e1f0346ef15062f1a668a6623f4fd96f7d289ca43d3de6cd009df496c4a 0.600000000000 1371012 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 913746, "vin": [ { "gen": { "height": 913736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1d22e1f0346ef15062f1a668a6623f4fd96f7d289ca43d3de6cd009df496c4a" } } ], "extra": [ 1, 77, 73, 182, 249, 205, 78, 236, 155, 155, 230, 10, 33, 10, 74, 152, 127, 252, 43, 223, 222, 55, 74, 25, 116, 190, 251, 191, 107, 81, 111, 206, 132, 2, 17, 0, 0, 0, 12, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8