Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93cbcd13b1839a6b418f37d133b916dd1c958644baf6528ec5e6ddf9ee1f47af

Tx prefix hash: 1af4459024ceee5c7097e01a7d8b018a1cc21fa1b5b25fc6d6427a449e69f286
Tx public key: 80f8897c66f180df64cce28ae5da49fc8d0f11d238bcaa887b32d3882a660de2
Timestamp: 1710485791 Timestamp [UCT]: 2024-03-15 06:56:31 Age [y:d:h:m:s]: 01:014:01:16:08
Block: 978695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271007 RingCT/type: yes/0
Extra: 0180f8897c66f180df64cce28ae5da49fc8d0f11d238bcaa887b32d3882a660de202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e0fa515e84395462dbb570cb08f1d3159b2402a7ba06deb79e6c412591f8b9d 0.600000000000 1438724 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": 978705, "vin": [ { "gen": { "height": 978695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e0fa515e84395462dbb570cb08f1d3159b2402a7ba06deb79e6c412591f8b9d" } } ], "extra": [ 1, 128, 248, 137, 124, 102, 241, 128, 223, 100, 204, 226, 138, 229, 218, 73, 252, 141, 15, 17, 210, 56, 188, 170, 136, 123, 50, 211, 136, 42, 102, 13, 226, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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