Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfa5cf2f873a2d746d52f46dc7a23f7ee31e5daed4ae0126523d6a708ef36a00

Tx prefix hash: 01841989e97f59eeaccfb2992ab28ef901934826b6c8a2f488ebf913dde531a6
Tx public key: 8a8259537eb60f319db3295671dfbbcf2d292339d1adfbcd91eea435a99e1d61
Timestamp: 1702179938 Timestamp [UCT]: 2023-12-10 03:45:38 Age [y:d:h:m:s]: 01:037:12:54:41
Block: 909818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288179 RingCT/type: yes/0
Extra: 018a8259537eb60f319db3295671dfbbcf2d292339d1adfbcd91eea435a99e1d61021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96898286d2aab1d342a4a5a07eb88ebbc69a0ab3baf75bcf1e1831aa7952161c 0.600000000000 1366941 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": 909828, "vin": [ { "gen": { "height": 909818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96898286d2aab1d342a4a5a07eb88ebbc69a0ab3baf75bcf1e1831aa7952161c" } } ], "extra": [ 1, 138, 130, 89, 83, 126, 182, 15, 49, 157, 179, 41, 86, 113, 223, 187, 207, 45, 41, 35, 57, 209, 173, 251, 205, 145, 238, 164, 53, 169, 158, 29, 97, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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