Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bacfabe23b1f282043b806b537303082c744d4d3d9ee6c221f7abb05f84fcdce

Tx prefix hash: c4441d0feb19daf825b0ff8e586c70b5712c5e4f6b6adfb5f7bce16a2226d1f7
Tx public key: 21bc0a294e442cbfd7ca3e6091d03bdd88c68d9b37b4436b5f9f72b8de1d6e13
Timestamp: 1709364159 Timestamp [UCT]: 2024-03-02 07:22:39 Age [y:d:h:m:s]: 00:315:20:50:53
Block: 969388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226102 RingCT/type: yes/0
Extra: 0121bc0a294e442cbfd7ca3e6091d03bdd88c68d9b37b4436b5f9f72b8de1d6e130211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf1ffd9eeb8b35ffececdec1b0aeafa911dc5259e6764fafafe4292f057e08bf 0.600000000000 1429217 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": 969398, "vin": [ { "gen": { "height": 969388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf1ffd9eeb8b35ffececdec1b0aeafa911dc5259e6764fafafe4292f057e08bf" } } ], "extra": [ 1, 33, 188, 10, 41, 78, 68, 44, 191, 215, 202, 62, 96, 145, 208, 59, 221, 136, 198, 141, 155, 55, 180, 67, 107, 95, 159, 114, 184, 222, 29, 110, 19, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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