Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3b0ac9a8840c50390628167cbb0fa6477a3d829566ea8da7f7c7307e4aab972

Tx prefix hash: eef2a1ad6b6e465f7c450406bdc180fbbfd3ac2617ff56ef78270556d9d4afa4
Tx public key: 19b7f3f4bd368a0d2d43becbdabaa791c2069b59484fad84f328c2339f38b20f
Timestamp: 1669663788 Timestamp [UCT]: 2022-11-28 19:29:48 Age [y:d:h:m:s]: 02:345:18:28:06
Block: 641141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766550 RingCT/type: yes/0
Extra: 0119b7f3f4bd368a0d2d43becbdabaa791c2069b59484fad84f328c2339f38b20f02110000000583600029000000000000000000

1 output(s) for total of 4.609286636000 dcy

stealth address amount amount idx
00: 08e969028d9d5695f02607f3af6f643078b9acce896d4fd8e7cf850484ad9378 4.609286636000 1080920 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": 641151, "vin": [ { "gen": { "height": 641141 } } ], "vout": [ { "amount": 4609286636, "target": { "key": "08e969028d9d5695f02607f3af6f643078b9acce896d4fd8e7cf850484ad9378" } } ], "extra": [ 1, 25, 183, 243, 244, 189, 54, 138, 13, 45, 67, 190, 203, 218, 186, 167, 145, 194, 6, 155, 89, 72, 79, 173, 132, 243, 40, 194, 51, 159, 56, 178, 15, 2, 17, 0, 0, 0, 5, 131, 96, 0, 41, 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