Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9637ea0fd6dd93f9bb4d9e60e3dde33fa9565cd9da4892cc17ab036fe27af28a

Tx prefix hash: 90e5d93ffcbbfe9579eb8eab0dfac507eade0ce2f01b5405bb10ea50c1878029
Tx public key: 49c2a6651e0ee0b9498820edc187fa30983f71fef9a1c5a46a0190b24c2b9d6f
Timestamp: 1702797812 Timestamp [UCT]: 2023-12-17 07:23:32 Age [y:d:h:m:s]: 01:034:06:42:35
Block: 914938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285813 RingCT/type: yes/0
Extra: 0149c2a6651e0ee0b9498820edc187fa30983f71fef9a1c5a46a0190b24c2b9d6f02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ed0731932d035fc288b28676e8167169541bf98bf5dcefc2a2649c96488e4c1 0.600000000000 1372298 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": 914948, "vin": [ { "gen": { "height": 914938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ed0731932d035fc288b28676e8167169541bf98bf5dcefc2a2649c96488e4c1" } } ], "extra": [ 1, 73, 194, 166, 101, 30, 14, 224, 185, 73, 136, 32, 237, 193, 135, 250, 48, 152, 63, 113, 254, 249, 161, 197, 164, 106, 1, 144, 178, 76, 43, 157, 111, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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