Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b27d93e152574fdb6a0f918d55893f8b20c1ddc96f4d0884a753cf6623b1d339

Tx prefix hash: 56506e56e0323bb2c7b46fba50ddf962d71d8af5b9e776b7e9ca160ee6a0997a
Tx public key: ce7ae3dda519dbf2d6bfd2c905972a7a742126c2459bd20ca2189ef1bd54d17e
Timestamp: 1720903281 Timestamp [UCT]: 2024-07-13 20:41:21 Age [y:d:h:m:s]: 00:264:07:58:56
Block: 1065054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188833 RingCT/type: yes/0
Extra: 01ce7ae3dda519dbf2d6bfd2c905972a7a742126c2459bd20ca2189ef1bd54d17e021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ef5bc6625771c47033e98d9cd162abe8c04a531804e9381334a2bf6dc0ae530 0.600000000000 1535597 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": 1065064, "vin": [ { "gen": { "height": 1065054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ef5bc6625771c47033e98d9cd162abe8c04a531804e9381334a2bf6dc0ae530" } } ], "extra": [ 1, 206, 122, 227, 221, 165, 25, 219, 242, 214, 191, 210, 201, 5, 151, 42, 122, 116, 33, 38, 194, 69, 155, 210, 12, 162, 24, 158, 241, 189, 84, 209, 126, 2, 17, 0, 0, 0, 9, 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