Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ef46727c169f54b513199c525999d46dd30684b8734fe2b2b4761a4247bb627

Tx prefix hash: 3ce415c39857926079dd4da31ed2445f47e7f5a773687060217a1be7d0897192
Tx public key: 891341a318a79e748d8c586817ae3b6586f38460c1802aa8a032ef5a94e72669
Timestamp: 1707853681 Timestamp [UCT]: 2024-02-13 19:48:01 Age [y:d:h:m:s]: 01:050:06:56:46
Block: 956852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296969 RingCT/type: yes/0
Extra: 01891341a318a79e748d8c586817ae3b6586f38460c1802aa8a032ef5a94e726690211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fdd3997839f143e610cb3b6b9efbf052b54536bcea7acf8f7e4376dc9bea480 0.600000000000 1416164 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": 956862, "vin": [ { "gen": { "height": 956852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fdd3997839f143e610cb3b6b9efbf052b54536bcea7acf8f7e4376dc9bea480" } } ], "extra": [ 1, 137, 19, 65, 163, 24, 167, 158, 116, 141, 140, 88, 104, 23, 174, 59, 101, 134, 243, 132, 96, 193, 128, 42, 168, 160, 50, 239, 90, 148, 231, 38, 105, 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