Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f4b6f0c57f87763b88f91965d245ab7b3c627f86d69f1283737eedafedb2cd0

Tx prefix hash: bbfaab7816e6c1626b0556620108a7d0e138b7e63d710bc81a7880e56713121a
Tx public key: 4ce29a51fa77e0f5859f6f2d5ebc074ddf8313b4bccb0d6bf767197a436dbbf3
Timestamp: 1707894407 Timestamp [UCT]: 2024-02-14 07:06:47 Age [y:d:h:m:s]: 01:050:08:29:05
Block: 957186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297035 RingCT/type: yes/0
Extra: 014ce29a51fa77e0f5859f6f2d5ebc074ddf8313b4bccb0d6bf767197a436dbbf30211000000026d0f39ce000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f28f0d09191497cf4b41f0aff0cab212712a8bb9dfcba4f2d12c4b48aca44433 0.600000000000 1416502 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": 957196, "vin": [ { "gen": { "height": 957186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f28f0d09191497cf4b41f0aff0cab212712a8bb9dfcba4f2d12c4b48aca44433" } } ], "extra": [ 1, 76, 226, 154, 81, 250, 119, 224, 245, 133, 159, 111, 45, 94, 188, 7, 77, 223, 131, 19, 180, 188, 203, 13, 107, 247, 103, 25, 122, 67, 109, 187, 243, 2, 17, 0, 0, 0, 2, 109, 15, 57, 206, 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