Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cdddcff3f6ea6f3f2589662606746eb50480b9db64673fd236c971be2c469d6

Tx prefix hash: 5ce74c8e562d95075f3bcc1081cddabccd8bac4047fa920374de4089b1396b34
Tx public key: 8fdbe0b6c92fb3d5cb2d26242745340d36eca08e72ab95635ec9fd10b1029bfd
Timestamp: 1705907231 Timestamp [UCT]: 2024-01-22 07:07:11 Age [y:d:h:m:s]: 01:073:00:06:02
Block: 940683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313286 RingCT/type: yes/0
Extra: 018fdbe0b6c92fb3d5cb2d26242745340d36eca08e72ab95635ec9fd10b1029bfd0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efa6f711b29932001eb86a35faf3c3b7fb1b5542fd36084ff81e32bf5cc7d9a2 0.600000000000 1398823 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": 940693, "vin": [ { "gen": { "height": 940683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efa6f711b29932001eb86a35faf3c3b7fb1b5542fd36084ff81e32bf5cc7d9a2" } } ], "extra": [ 1, 143, 219, 224, 182, 201, 47, 179, 213, 203, 45, 38, 36, 39, 69, 52, 13, 54, 236, 160, 142, 114, 171, 149, 99, 94, 201, 253, 16, 177, 2, 155, 253, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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