Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 273a37e4aba39a8ae5f46ff4b0b59a4a70b01a7071b3c183e705a1f395cbc7ac

Tx prefix hash: 6a94e3ed76eb98415966004074d0595385b354a99365e33925322c22fc892e53
Tx public key: 558e03e820ab053fae71eb0a43179a13f2111ded183bba50718d9fd8e9fcdc5d
Timestamp: 1713208705 Timestamp [UCT]: 2024-04-15 19:18:25 Age [y:d:h:m:s]: 01:202:13:13:11
Block: 1001233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403431 RingCT/type: yes/0
Extra: 01558e03e820ab053fae71eb0a43179a13f2111ded183bba50718d9fd8e9fcdc5d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7a4ba5e740ebcb934f16d5d73412f7a349a33a115c094eb29204a5fd41cdc3b 0.600000000000 1461737 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": 1001243, "vin": [ { "gen": { "height": 1001233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7a4ba5e740ebcb934f16d5d73412f7a349a33a115c094eb29204a5fd41cdc3b" } } ], "extra": [ 1, 85, 142, 3, 232, 32, 171, 5, 63, 174, 113, 235, 10, 67, 23, 154, 19, 242, 17, 29, 237, 24, 59, 186, 80, 113, 141, 159, 216, 233, 252, 220, 93, 2, 17, 0, 0, 0, 3, 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