Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e103f3cafe945a8bde02a9571acbaaffda3ee7f7332d618158c2aa21d3c7d87f

Tx prefix hash: 05a0b51d0cd33dca81a5f245e1747cd4ffd77e441e885b2bc8a7c43f9aa0b956
Tx public key: acd07dafd871ed2e4d34f4fb3fd660d7cc4f1011bbac6c31b93ae9277a3db969
Timestamp: 1727952289 Timestamp [UCT]: 2024-10-03 10:44:49 Age [y:d:h:m:s]: 00:176:02:01:55
Block: 1123485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125643 RingCT/type: yes/0
Extra: 01acd07dafd871ed2e4d34f4fb3fd660d7cc4f1011bbac6c31b93ae9277a3db969021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8495f599aa1b86330f1071847bda28cfeb49a887a7f7a2e6c63cbacc488ef0b7 0.600000000000 1606020 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": 1123495, "vin": [ { "gen": { "height": 1123485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8495f599aa1b86330f1071847bda28cfeb49a887a7f7a2e6c63cbacc488ef0b7" } } ], "extra": [ 1, 172, 208, 125, 175, 216, 113, 237, 46, 77, 52, 244, 251, 63, 214, 96, 215, 204, 79, 16, 17, 187, 172, 108, 49, 185, 58, 233, 39, 122, 61, 185, 105, 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