Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b613952067606dee0cc5ae722dd34056d601535c14cf3c231c036b5e702567f

Tx prefix hash: af040e9484f6d9f44c197c89bfcefc95af8ed4bef1e95a31480c9670a3ef60ae
Tx public key: 24fb83eed1823b8c6bf0cc69913aa50dc46f6bc9cbb8242b78526404c8562103
Timestamp: 1725218574 Timestamp [UCT]: 2024-09-01 19:22:54 Age [y:d:h:m:s]: 00:083:12:30:12
Block: 1100826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59724 RingCT/type: yes/0
Extra: 0124fb83eed1823b8c6bf0cc69913aa50dc46f6bc9cbb8242b78526404c8562103021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d11bb6807f103b8af5f49aee0e96fcbe5dcff8788b2a08f13b6bb0cb40ee044 0.600000000000 1576807 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": 1100836, "vin": [ { "gen": { "height": 1100826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d11bb6807f103b8af5f49aee0e96fcbe5dcff8788b2a08f13b6bb0cb40ee044" } } ], "extra": [ 1, 36, 251, 131, 238, 209, 130, 59, 140, 107, 240, 204, 105, 145, 58, 165, 13, 196, 111, 107, 201, 203, 184, 36, 43, 120, 82, 100, 4, 200, 86, 33, 3, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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