Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3840e296e1118ffc90e1622d4e3cdf385ed066e566b9be0774f4791eda6f534a

Tx prefix hash: 739382dfc0b2a2b49ed16915cdc5de8db6dd681850430d270843bdaa26ffbbf9
Tx public key: 9fd97339ce78e84c3c1da903b7bf67bf1e5b6b2540d7e8f777f1fa6faea79478
Timestamp: 1698111932 Timestamp [UCT]: 2023-10-24 01:45:32 Age [y:d:h:m:s]: 01:097:21:43:29
Block: 876299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330953 RingCT/type: yes/0
Extra: 019fd97339ce78e84c3c1da903b7bf67bf1e5b6b2540d7e8f777f1fa6faea7947802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.766403822000 dcy

stealth address amount amount idx
00: 2fb155628447c9d4887a341f9e961ca4e628fd21f12836df8d0067156e237de2 0.766403822000 1331617 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": 876309, "vin": [ { "gen": { "height": 876299 } } ], "vout": [ { "amount": 766403822, "target": { "key": "2fb155628447c9d4887a341f9e961ca4e628fd21f12836df8d0067156e237de2" } } ], "extra": [ 1, 159, 217, 115, 57, 206, 120, 232, 76, 60, 29, 169, 3, 183, 191, 103, 191, 30, 91, 107, 37, 64, 215, 232, 247, 119, 241, 250, 111, 174, 167, 148, 120, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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