Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fc5de4f19e6f03620475631ed4ba900ff09f50801b6e2091cdc7fb8120d39e0

Tx prefix hash: f28af86a85d3e66dc222f294fe67a67eb895f5ca9a0f8283af51776230617c56
Tx public key: c6c27c9c8f3279329d544416efad34ff87dde1a84ae084291eb936efdbc319fb
Timestamp: 1701009157 Timestamp [UCT]: 2023-11-26 14:32:37 Age [y:d:h:m:s]: 02:042:21:16:31
Block: 900105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550486 RingCT/type: yes/0
Extra: 01c6c27c9c8f3279329d544416efad34ff87dde1a84ae084291eb936efdbc319fb021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.639114200000 dcy

stealth address amount amount idx
00: a154b673263f8456262f237a09743b4b1a51933f3bbb488f1c816e3a40762b16 0.639114200000 1356582 of 0

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": 900115, "vin": [ { "gen": { "height": 900105 } } ], "vout": [ { "amount": 639114200, "target": { "key": "a154b673263f8456262f237a09743b4b1a51933f3bbb488f1c816e3a40762b16" } } ], "extra": [ 1, 198, 194, 124, 156, 143, 50, 121, 50, 157, 84, 68, 22, 239, 173, 52, 255, 135, 221, 225, 168, 74, 224, 132, 41, 30, 185, 54, 239, 219, 195, 25, 251, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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