Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7af8a69c3798397457505c1ddb9a392dc50c56f787be34e1405f42c98a1d034d

Tx prefix hash: 2416d6fd7ea842177d593354f5a5338c2776bd0d5e4a40ac4cef7dac8d126e18
Tx public key: 8ee1eaf77de416519bf90e2a90dfe0b39c4617e4dcafede13d1ac1018b5d7cec
Timestamp: 1732366989 Timestamp [UCT]: 2024-11-23 13:03:09 Age [y:d:h:m:s]: 00:187:14:49:09
Block: 1159986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133947 RingCT/type: yes/0
Extra: 018ee1eaf77de416519bf90e2a90dfe0b39c4617e4dcafede13d1ac1018b5d7cec021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efc1e65cef76b29e0f097779552fab0c78011292a073211ddf99a0ac07b33f73 0.600000000000 1645627 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": 1159996, "vin": [ { "gen": { "height": 1159986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efc1e65cef76b29e0f097779552fab0c78011292a073211ddf99a0ac07b33f73" } } ], "extra": [ 1, 142, 225, 234, 247, 125, 228, 22, 81, 155, 249, 14, 42, 144, 223, 224, 179, 156, 70, 23, 228, 220, 175, 237, 225, 61, 26, 193, 1, 139, 93, 124, 236, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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