Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcc6938a9582b6ed7189bbca80f763a26e410d2bb9e29092166392a991753872

Tx prefix hash: c1a3a50e1eb00786ab39f75174e4dbd76ac07a9d1ffcd37bcace829adc5a08a6
Tx public key: 6bbfb193811f2e14c5241c3b26e9170b1f3313ff1ac02f6323cd252f271b294c
Timestamp: 1726010465 Timestamp [UCT]: 2024-09-10 23:21:05 Age [y:d:h:m:s]: 00:211:06:51:32
Block: 1107387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150841 RingCT/type: yes/0
Extra: 016bbfb193811f2e14c5241c3b26e9170b1f3313ff1ac02f6323cd252f271b294c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 933e2700d1c3b89b05f8e33c822c2329770952365826dfd83806e92d3ba285e3 0.600000000000 1584998 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": 1107397, "vin": [ { "gen": { "height": 1107387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "933e2700d1c3b89b05f8e33c822c2329770952365826dfd83806e92d3ba285e3" } } ], "extra": [ 1, 107, 191, 177, 147, 129, 31, 46, 20, 197, 36, 28, 59, 38, 233, 23, 11, 31, 51, 19, 255, 26, 192, 47, 99, 35, 205, 37, 47, 39, 27, 41, 76, 2, 17, 0, 0, 0, 5, 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