Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c503cef983d562a62717e88a4cc3710126e722206f63c0da9f24e11a589cfdb4

Tx prefix hash: 878ddaa1829247313588fdb3002a5da653b5c3ee1eddfdd761534594815cb4b4
Tx public key: 0da3671d1be2e2c3916b6a22c1c2dcc39ff29aca8941c60bf61e4195903ffcb8
Timestamp: 1693254614 Timestamp [UCT]: 2023-08-28 20:30:14 Age [y:d:h:m:s]: 01:220:00:49:41
Block: 835999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418384 RingCT/type: yes/0
Extra: 010da3671d1be2e2c3916b6a22c1c2dcc39ff29aca8941c60bf61e4195903ffcb802110000000227f2911c000000000000000000

1 output(s) for total of 1.042289471000 dcy

stealth address amount amount idx
00: 1f4bff51e7fc797e8ce220286a28f0f641491a8e6cefe73efa22871a0f3d2c9d 1.042289471000 1288573 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": 836009, "vin": [ { "gen": { "height": 835999 } } ], "vout": [ { "amount": 1042289471, "target": { "key": "1f4bff51e7fc797e8ce220286a28f0f641491a8e6cefe73efa22871a0f3d2c9d" } } ], "extra": [ 1, 13, 163, 103, 29, 27, 226, 226, 195, 145, 107, 106, 34, 193, 194, 220, 195, 159, 242, 154, 202, 137, 65, 198, 11, 246, 30, 65, 149, 144, 63, 252, 184, 2, 17, 0, 0, 0, 2, 39, 242, 145, 28, 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