Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b531c6b000e45f06f2e511c9562130113d1633d5dec428f63a23fdc3891791b7

Tx prefix hash: 8b97100ebbea68668f5237e4d2a5691900b79c6c30a6d180d31b269855efdd2f
Tx public key: 0df8738d2d2c78930c04a1dac4fb33fe7e27460bad4b9d0ec0298d334c603145
Timestamp: 1734001381 Timestamp [UCT]: 2024-12-12 11:03:01 Age [y:d:h:m:s]: 00:102:13:08:11
Block: 1173547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73053 RingCT/type: yes/0
Extra: 010df8738d2d2c78930c04a1dac4fb33fe7e27460bad4b9d0ec0298d334c603145021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d2cf0252c7cf1f31ef244cb7f90f07092668b67511442519ead2efacb879c71 0.600000000000 1659582 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": 1173557, "vin": [ { "gen": { "height": 1173547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d2cf0252c7cf1f31ef244cb7f90f07092668b67511442519ead2efacb879c71" } } ], "extra": [ 1, 13, 248, 115, 141, 45, 44, 120, 147, 12, 4, 161, 218, 196, 251, 51, 254, 126, 39, 70, 11, 173, 75, 157, 14, 192, 41, 141, 51, 76, 96, 49, 69, 2, 17, 0, 0, 0, 5, 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