Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf60bf47f321a9d4e9e4b8ae194e240907e77bcd9c270a9f06b9e3e86c47e200

Tx prefix hash: dcdf30ae2c4f89f29b72a3e0ea4dcf658893d0640e5102a2d0f4496d6f8b4f4a
Tx public key: f3b28006dce2aa95b1c5a4e5860673d6ca1f854f8e55cdf0d76666ade4051fab
Timestamp: 1702401648 Timestamp [UCT]: 2023-12-12 17:20:48 Age [y:d:h:m:s]: 01:331:14:34:25
Block: 911675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495838 RingCT/type: yes/0
Extra: 01f3b28006dce2aa95b1c5a4e5860673d6ca1f854f8e55cdf0d76666ade4051fab02110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb41011409f952a111bc75e6a703cdc7aeb5a2d2304874707eb6809b5bee11d0 0.600000000000 1368889 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": 911685, "vin": [ { "gen": { "height": 911675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb41011409f952a111bc75e6a703cdc7aeb5a2d2304874707eb6809b5bee11d0" } } ], "extra": [ 1, 243, 178, 128, 6, 220, 226, 170, 149, 177, 197, 164, 229, 134, 6, 115, 214, 202, 31, 133, 79, 142, 85, 205, 240, 215, 102, 102, 173, 228, 5, 31, 171, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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