Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d74b4454e7e81ef1af30447b2ef0d80fbcf203fc50ce61b1dd19126a59183e2

Tx prefix hash: d439bd61aad5ea776c133eaa5fa72326fd2c14920c1f6990c85fc7aa32422a5f
Tx public key: f0e49eb7e5300c2ceecc096616cf85ac998a87279466d1c364c984e3110f99e8
Timestamp: 1728820410 Timestamp [UCT]: 2024-10-13 11:53:30 Age [y:d:h:m:s]: 01:026:15:59:37
Block: 1130684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277422 RingCT/type: yes/0
Extra: 01f0e49eb7e5300c2ceecc096616cf85ac998a87279466d1c364c984e3110f99e8021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6faf07956fd4f3ec1a9c7dc0c0d9fa3d0f9b776d57847151150e351ee27c4d95 0.600000000000 1613561 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": 1130694, "vin": [ { "gen": { "height": 1130684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6faf07956fd4f3ec1a9c7dc0c0d9fa3d0f9b776d57847151150e351ee27c4d95" } } ], "extra": [ 1, 240, 228, 158, 183, 229, 48, 12, 44, 238, 204, 9, 102, 22, 207, 133, 172, 153, 138, 135, 39, 148, 102, 209, 195, 100, 201, 132, 227, 17, 15, 153, 232, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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