Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c3487724f7ab6db31d183a1b0beaf09f1226decf4c0b175ee36de4034bc8d80

Tx prefix hash: 811cca6155579694f3b28343a35a52ddc5bad33fc5f723f3198f9f8bd55f0db5
Tx public key: 7813eeebe58b7c4ab75eb11a218a66af3ed070081d85d195fb3813fb0d197b41
Timestamp: 1721471592 Timestamp [UCT]: 2024-07-20 10:33:12 Age [y:d:h:m:s]: 00:254:03:03:55
Block: 1069754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181543 RingCT/type: yes/0
Extra: 017813eeebe58b7c4ab75eb11a218a66af3ed070081d85d195fb3813fb0d197b41021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 258267402095a374f16c7fb71210480de7c2b6e9d614ca1f5d2f84c314f66443 0.600000000000 1541311 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": 1069764, "vin": [ { "gen": { "height": 1069754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "258267402095a374f16c7fb71210480de7c2b6e9d614ca1f5d2f84c314f66443" } } ], "extra": [ 1, 120, 19, 238, 235, 229, 139, 124, 74, 183, 94, 177, 26, 33, 138, 102, 175, 62, 208, 112, 8, 29, 133, 209, 149, 251, 56, 19, 251, 13, 25, 123, 65, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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