Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbf62f1e6ec2d52b506b149abf3a4bb4c71fe8c5fa3b0784103f9c408d447e30

Tx prefix hash: bc341ab3e45810a153a01bcdb77e94ab9bf78f9f31fe09212adec7099029b1fa
Tx public key: 87a660fbaa90867bf46edbe65edcb2d39c4d1e4d8270c7cf1c4694fe2d780ca3
Timestamp: 1730942720 Timestamp [UCT]: 2024-11-07 01:25:20 Age [y:d:h:m:s]: 00:058:12:18:15
Block: 1148193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41872 RingCT/type: yes/0
Extra: 0187a660fbaa90867bf46edbe65edcb2d39c4d1e4d8270c7cf1c4694fe2d780ca30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbace80da67b665c9415ae808dc1775f067daef8fd9a2129297cc3bfb0100d06 0.600000000000 1632984 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": 1148203, "vin": [ { "gen": { "height": 1148193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbace80da67b665c9415ae808dc1775f067daef8fd9a2129297cc3bfb0100d06" } } ], "extra": [ 1, 135, 166, 96, 251, 170, 144, 134, 123, 244, 110, 219, 230, 94, 220, 178, 211, 156, 77, 30, 77, 130, 112, 199, 207, 28, 70, 148, 254, 45, 120, 12, 163, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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