Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc9d7e2692ffd11cf0444704d99c5366438199fcb634465fc01c4c7c754b64e5

Tx prefix hash: 3645c6acf33443a2680741764db4192af1d081d11156d862feb419189a47aa2f
Tx public key: c054ba4e9e912e5b95aaeee8db7cf7a97a41a590c27e4ff34a915e7111364150
Timestamp: 1724326964 Timestamp [UCT]: 2024-08-22 11:42:44 Age [y:d:h:m:s]: 00:227:22:17:07
Block: 1093445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162744 RingCT/type: yes/0
Extra: 01c054ba4e9e912e5b95aaeee8db7cf7a97a41a590c27e4ff34a915e711136415002110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b435e6d1242ac814965cf42f13d031d14f82d21ff28a4bda998d98fbe9760c27 0.600000000000 1568390 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": 1093455, "vin": [ { "gen": { "height": 1093445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b435e6d1242ac814965cf42f13d031d14f82d21ff28a4bda998d98fbe9760c27" } } ], "extra": [ 1, 192, 84, 186, 78, 158, 145, 46, 91, 149, 170, 238, 232, 219, 124, 247, 169, 122, 65, 165, 144, 194, 126, 79, 243, 74, 145, 94, 113, 17, 54, 65, 80, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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