Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf362f87d3cc92b4b82474092ee6d8dd054ffedb208c6e05b8f50dd8dabd3830

Tx prefix hash: e7929d436f1a300d34a2305004573346e5f352d988e96f471ac84b580b1af9f9
Tx public key: b5e215e1c99ee3ff1b38f536588abbda95f067a384fc4c6a646a329e9d5fe91f
Timestamp: 1708233312 Timestamp [UCT]: 2024-02-18 05:15:12 Age [y:d:h:m:s]: 01:049:18:54:31
Block: 960002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296599 RingCT/type: yes/0
Extra: 01b5e215e1c99ee3ff1b38f536588abbda95f067a384fc4c6a646a329e9d5fe91f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cfe9efc9e41f0657ffe85f91f60b3c2747650c3eb761243e3774c440d879089 0.600000000000 1419561 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": 960012, "vin": [ { "gen": { "height": 960002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cfe9efc9e41f0657ffe85f91f60b3c2747650c3eb761243e3774c440d879089" } } ], "extra": [ 1, 181, 226, 21, 225, 201, 158, 227, 255, 27, 56, 245, 54, 88, 138, 187, 218, 149, 240, 103, 163, 132, 252, 76, 106, 100, 106, 50, 158, 157, 95, 233, 31, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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