Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50c09f0dae8a48dee17708a0fcbf7ae479aa1737d0a33f9809a7bf7a46f9784e

Tx prefix hash: 23497cd9cdecc0411ca02e68ca2a5814ff5958e1ebcfe43839079c7d31458a98
Tx public key: 1fb5a0e5fca98dbf3e55a61f75fef51fe71b927db70d35f84798c17be990967f
Timestamp: 1635983977 Timestamp [UCT]: 2021-11-03 23:59:37 Age [y:d:h:m:s]: 03:050:08:11:58
Block: 366789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 814551 RingCT/type: yes/0
Extra: 011fb5a0e5fca98dbf3e55a61f75fef51fe71b927db70d35f84798c17be990967f02110000000337cb3088000000000000000000

1 output(s) for total of 37.383174729000 dcy

stealth address amount amount idx
00: a757aac7851d91fb0b01793b1abff45cd892ea43454d2d994808562176cbc5f8 37.383174729000 744447 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": 366799, "vin": [ { "gen": { "height": 366789 } } ], "vout": [ { "amount": 37383174729, "target": { "key": "a757aac7851d91fb0b01793b1abff45cd892ea43454d2d994808562176cbc5f8" } } ], "extra": [ 1, 31, 181, 160, 229, 252, 169, 141, 191, 62, 85, 166, 31, 117, 254, 245, 31, 231, 27, 146, 125, 183, 13, 53, 248, 71, 152, 193, 123, 233, 144, 150, 127, 2, 17, 0, 0, 0, 3, 55, 203, 48, 136, 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