Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18f641b2babcaf43d289bdc23c6e4d53a760dec642e8107b222b12c540ae53f8

Tx prefix hash: e6dbeb6a70ae692e7e98a96109fa858b5f60db5da27868fb2a09d02182d37a4c
Tx public key: 463bd44d8cd0b1003ea2c3b88265da6138c1db92b1c736e588bf0fa50044c44c
Timestamp: 1730668685 Timestamp [UCT]: 2024-11-03 21:18:05 Age [y:d:h:m:s]: 00:174:17:44:17
Block: 1145925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124733 RingCT/type: yes/0
Extra: 01463bd44d8cd0b1003ea2c3b88265da6138c1db92b1c736e588bf0fa50044c44c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bd13489e547167179233b7376a75f27e877f6d40df8e1f95d95a272ea2c4ff7 0.600000000000 1630456 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": 1145935, "vin": [ { "gen": { "height": 1145925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bd13489e547167179233b7376a75f27e877f6d40df8e1f95d95a272ea2c4ff7" } } ], "extra": [ 1, 70, 59, 212, 77, 140, 208, 177, 0, 62, 162, 195, 184, 130, 101, 218, 97, 56, 193, 219, 146, 177, 199, 54, 229, 136, 191, 15, 165, 0, 68, 196, 76, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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