Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 637021ce63c377e21fc4cfd97bfa70d58e8e5fd294b6821d7320d97678a018a1

Tx prefix hash: 391fd1bdf15b68cae0af1e4dc06eb5eaae0796e26f3d70fc429b17b6d2132c1e
Tx public key: 59eb22ddfea4a3f47fcb614f853583478c9ad1a24ac68c4487255b12a6cf26c4
Timestamp: 1738144849 Timestamp [UCT]: 2025-01-29 10:00:49 Age [y:d:h:m:s]: 00:139:06:23:43
Block: 1207567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99497 RingCT/type: yes/0
Extra: 0159eb22ddfea4a3f47fcb614f853583478c9ad1a24ac68c4487255b12a6cf26c4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 690c9676c3ac756d652e4074ce92e9c2effbecf10305e17a959dbde52ecc920e 0.600000000000 1694292 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": 1207577, "vin": [ { "gen": { "height": 1207567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "690c9676c3ac756d652e4074ce92e9c2effbecf10305e17a959dbde52ecc920e" } } ], "extra": [ 1, 89, 235, 34, 221, 254, 164, 163, 244, 127, 203, 97, 79, 133, 53, 131, 71, 140, 154, 209, 162, 74, 198, 140, 68, 135, 37, 91, 18, 166, 207, 38, 196, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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