Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c133c37088503fd10829c5cc0a71c81bd75af7c5ae6911f534181580e87799de

Tx prefix hash: d8e1cf2c7bde45b6f084c720ce8ae977d2407f23b987e548103fca27e8198b90
Tx public key: 02ea288ee3b9d0f66b50b907ba7ca51b91dcbbfa188080b115b1cef30b9ab5f4
Timestamp: 1722910075 Timestamp [UCT]: 2024-08-06 02:07:55 Age [y:d:h:m:s]: 00:297:03:25:49
Block: 1081676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212303 RingCT/type: yes/0
Extra: 0102ea288ee3b9d0f66b50b907ba7ca51b91dcbbfa188080b115b1cef30b9ab5f4021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7e00d61f12d09b391fa41593f99bf6d7a6f87eb2db12f0313bd33946d297f42 0.600000000000 1555493 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": 1081686, "vin": [ { "gen": { "height": 1081676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7e00d61f12d09b391fa41593f99bf6d7a6f87eb2db12f0313bd33946d297f42" } } ], "extra": [ 1, 2, 234, 40, 142, 227, 185, 208, 246, 107, 80, 185, 7, 186, 124, 165, 27, 145, 220, 187, 250, 24, 128, 128, 177, 21, 177, 206, 243, 11, 154, 181, 244, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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