Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f81bc3ce71ed7b4aaa54fe1cf39579ca9e8bcef176a4aaff4082bd77f7b11c3

Tx prefix hash: 360c53a6feaad51c58dfe6d4e1e7a1545d203d2a0aee10d00d0d088073e189a0
Tx public key: e8c030893356c20888e6b053b42bcec408d5e6698ebc7a8aee996b3a94bf32be
Timestamp: 1721556887 Timestamp [UCT]: 2024-07-21 10:14:47 Age [y:d:h:m:s]: 00:187:12:41:11
Block: 1070452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134139 RingCT/type: yes/0
Extra: 01e8c030893356c20888e6b053b42bcec408d5e6698ebc7a8aee996b3a94bf32be021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f466313d9533a0f49586afd8e403a9eba49443e3ce6161d7fca2eec84922c5f 0.600000000000 1542293 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": 1070462, "vin": [ { "gen": { "height": 1070452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f466313d9533a0f49586afd8e403a9eba49443e3ce6161d7fca2eec84922c5f" } } ], "extra": [ 1, 232, 192, 48, 137, 51, 86, 194, 8, 136, 230, 176, 83, 180, 43, 206, 196, 8, 213, 230, 105, 142, 188, 122, 138, 238, 153, 107, 58, 148, 191, 50, 190, 2, 17, 0, 0, 0, 5, 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