Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f674464e529257c9d30139a5b07bd1f1fc2a600d132385e56384eee79466c12

Tx prefix hash: cfb8db6cc2375cfe60b701da6d701342ebf3ac07750c7038335d483c6e9adb6c
Tx public key: 57771f8dd8f6d0e38eace4745f36dbcaae914ac9d0f8f073f3f8d1810ec4ceb7
Timestamp: 1724099862 Timestamp [UCT]: 2024-08-19 20:37:42 Age [y:d:h:m:s]: 00:302:17:33:18
Block: 1091550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216146 RingCT/type: yes/0
Extra: 0157771f8dd8f6d0e38eace4745f36dbcaae914ac9d0f8f073f3f8d1810ec4ceb702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e089ffe94dfe943f7326be807d1118d3d8f3935fe679fceb0ad5325cf29ea8af 0.600000000000 1566183 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": 1091560, "vin": [ { "gen": { "height": 1091550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e089ffe94dfe943f7326be807d1118d3d8f3935fe679fceb0ad5325cf29ea8af" } } ], "extra": [ 1, 87, 119, 31, 141, 216, 246, 208, 227, 142, 172, 228, 116, 95, 54, 219, 202, 174, 145, 74, 201, 208, 248, 240, 115, 243, 248, 209, 129, 14, 196, 206, 183, 2, 17, 0, 0, 0, 3, 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