Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559df9ed78967caedf873108265b6a1250e57d8a9c045dc4037083bac53b411c

Tx prefix hash: cc54615f6bc6dad7a414ad49e014a8c0fa7ac3449774c65ff1cafed00bfe34d3
Tx public key: b454ca4803e575a7a40167344f39f3f8652293fd21fd1f8e59eb1d6b5255c45f
Timestamp: 1711006699 Timestamp [UCT]: 2024-03-21 07:38:19 Age [y:d:h:m:s]: 01:010:10:06:16
Block: 983014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268400 RingCT/type: yes/0
Extra: 01b454ca4803e575a7a40167344f39f3f8652293fd21fd1f8e59eb1d6b5255c45f0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7b41cc1016c039c8085ad0ea1000ee7effc4074d402cb48616cbe08df3ff40e 0.600000000000 1443133 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": 983024, "vin": [ { "gen": { "height": 983014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7b41cc1016c039c8085ad0ea1000ee7effc4074d402cb48616cbe08df3ff40e" } } ], "extra": [ 1, 180, 84, 202, 72, 3, 229, 117, 167, 164, 1, 103, 52, 79, 57, 243, 248, 101, 34, 147, 253, 33, 253, 31, 142, 89, 235, 29, 107, 82, 85, 196, 95, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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