Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 730b5e8ef12d74e3a1af860d4f33fe2f9271254f274421d108b750ec4cd3a1d6

Tx prefix hash: f1229bdd512caa31df671c413a058f6dd27fc1925f430eed5740e9d2b92b6f04
Tx public key: 538a8030d01c4cd0a0e226769f946fce1e78d2317ddebdbca40a34b56543932c
Timestamp: 1712011956 Timestamp [UCT]: 2024-04-01 22:52:36 Age [y:d:h:m:s]: 00:274:13:49:37
Block: 991296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196582 RingCT/type: yes/0
Extra: 01538a8030d01c4cd0a0e226769f946fce1e78d2317ddebdbca40a34b56543932c0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0107c7591c74e8659f1e61cc46d61255753f56d969c2eb8be4d61b54978dc32 0.600000000000 1451630 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": 991306, "vin": [ { "gen": { "height": 991296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0107c7591c74e8659f1e61cc46d61255753f56d969c2eb8be4d61b54978dc32" } } ], "extra": [ 1, 83, 138, 128, 48, 208, 28, 76, 208, 160, 226, 38, 118, 159, 148, 111, 206, 30, 120, 210, 49, 125, 222, 189, 188, 164, 10, 52, 181, 101, 67, 147, 44, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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