Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1c048afeee0bcd3a4c5506698968c1f137e19404e0bf09530670b3209e3712f

Tx prefix hash: b01d75604ebe1e005cb50314237cdfa698e691270eeaabcf2b5bed5d490a5233
Tx public key: eff0be65be8314805b5809510e894e4c98a275e1b1a0ddf5b5ab197c9b281859
Timestamp: 1720164544 Timestamp [UCT]: 2024-07-05 07:29:04 Age [y:d:h:m:s]: 01:131:06:14:13
Block: 1058909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352354 RingCT/type: yes/0
Extra: 01eff0be65be8314805b5809510e894e4c98a275e1b1a0ddf5b5ab197c9b2818590211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9df2ea03e9ff031130b3eab5a12dd3170ff9df1bf4026a7c5880431216153e59 0.600000000000 1529368 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": 1058919, "vin": [ { "gen": { "height": 1058909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9df2ea03e9ff031130b3eab5a12dd3170ff9df1bf4026a7c5880431216153e59" } } ], "extra": [ 1, 239, 240, 190, 101, 190, 131, 20, 128, 91, 88, 9, 81, 14, 137, 78, 76, 152, 162, 117, 225, 177, 160, 221, 245, 181, 171, 25, 124, 155, 40, 24, 89, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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