Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15793335ff52d75500719c72edf1aadc1f571823acff2f0c99b30f252a3cc071

Tx prefix hash: 4fd9854e6fd8c8f4a155cf1ff10a718e91f9bdd504c4bd976335897e8e479a1f
Tx public key: a9c09c17c605e5e6199f0b7448932305c420da8370781ea1433d9eb24d75f229
Timestamp: 1702103077 Timestamp [UCT]: 2023-12-09 06:24:37 Age [y:d:h:m:s]: 01:359:08:29:17
Block: 909174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515732 RingCT/type: yes/0
Extra: 01a9c09c17c605e5e6199f0b7448932305c420da8370781ea1433d9eb24d75f229021100000007faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a7b94866f22bbd729ae733ee6d9ff1b688407f6b8a7eb27dac435b856fd955e 0.600000000000 1366243 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": 909184, "vin": [ { "gen": { "height": 909174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a7b94866f22bbd729ae733ee6d9ff1b688407f6b8a7eb27dac435b856fd955e" } } ], "extra": [ 1, 169, 192, 156, 23, 198, 5, 229, 230, 25, 159, 11, 116, 72, 147, 35, 5, 196, 32, 218, 131, 112, 120, 30, 161, 67, 61, 158, 178, 77, 117, 242, 41, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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