Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fd5f743d9d6d5f230a693bc21c2be11906efd272b4c0b20b2ee5d6827016f88

Tx prefix hash: 902d5cc40fbd35b5c3f456a679f42432962ba3f6e9fdc189b59efd89a46c288d
Tx public key: 53bf01f80c0a8e3ca6e0a94cb32dfbc6c8cd56ae9533de5ae464a70d149b669b
Timestamp: 1710409226 Timestamp [UCT]: 2024-03-14 09:40:26 Age [y:d:h:m:s]: 01:137:14:34:32
Block: 978067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358217 RingCT/type: yes/0
Extra: 0153bf01f80c0a8e3ca6e0a94cb32dfbc6c8cd56ae9533de5ae464a70d149b669b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50a64a5a9e006b00592a879661813bd42d1b1b862bc003cc656ae86abdeaf7b1 0.600000000000 1438084 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": 978077, "vin": [ { "gen": { "height": 978067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50a64a5a9e006b00592a879661813bd42d1b1b862bc003cc656ae86abdeaf7b1" } } ], "extra": [ 1, 83, 191, 1, 248, 12, 10, 142, 60, 166, 224, 169, 76, 179, 45, 251, 198, 200, 205, 86, 174, 149, 51, 222, 90, 228, 100, 167, 13, 20, 155, 102, 155, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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