Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19314012f0bcdc27b762aa0519fd52de9ddde2ce14b71518592a547c3202f483

Tx prefix hash: bd33f26a201eb4a5c9584ad0220e4b6b6eeff85346615e81c9c36f60bcbaf406
Tx public key: 7399bc715d34d30d781fadae6d5a8b09d7337a4182946571ee6b0d897cae96f2
Timestamp: 1703804100 Timestamp [UCT]: 2023-12-28 22:55:00 Age [y:d:h:m:s]: 01:358:23:45:25
Block: 923285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515449 RingCT/type: yes/0
Extra: 017399bc715d34d30d781fadae6d5a8b09d7337a4182946571ee6b0d897cae96f2021100000001ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d1bf6db71bc6e1436c62ce6e3fc02d85abe6c2a31e6df8d21b31a21a64935c3 0.600000000000 1381013 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": 923295, "vin": [ { "gen": { "height": 923285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d1bf6db71bc6e1436c62ce6e3fc02d85abe6c2a31e6df8d21b31a21a64935c3" } } ], "extra": [ 1, 115, 153, 188, 113, 93, 52, 211, 13, 120, 31, 173, 174, 109, 90, 139, 9, 215, 51, 122, 65, 130, 148, 101, 113, 238, 107, 13, 137, 124, 174, 150, 242, 2, 17, 0, 0, 0, 1, 173, 86, 148, 172, 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