Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d730ba860306c781fa240bd6a01c1ad2a1b60a5fca7228aa83874a59533bf4d7

Tx prefix hash: a8592a92e246fc2de01930904e6313dbc3f905faf738a97a619ab70c8ec6e73e
Tx public key: 34798b5382072cdbe081f131a0b1410376d4e3eda5aeb0afc348a55b3ed55a0c
Timestamp: 1736257434 Timestamp [UCT]: 2025-01-07 13:43:54 Age [y:d:h:m:s]: 00:092:14:37:45
Block: 1192204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65972 RingCT/type: yes/0
Extra: 0134798b5382072cdbe081f131a0b1410376d4e3eda5aeb0afc348a55b3ed55a0c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1118999d8bb3f7b3c850eeed2ae343a6038c49cbfd3bee9b20e7450f58c5856d 0.600000000000 1678753 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": 1192214, "vin": [ { "gen": { "height": 1192204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1118999d8bb3f7b3c850eeed2ae343a6038c49cbfd3bee9b20e7450f58c5856d" } } ], "extra": [ 1, 52, 121, 139, 83, 130, 7, 44, 219, 224, 129, 241, 49, 160, 177, 65, 3, 118, 212, 227, 237, 165, 174, 176, 175, 195, 72, 165, 91, 62, 213, 90, 12, 2, 17, 0, 0, 0, 1, 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