Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0386a78643be5580fdb0930d7f40ab63641f3a4ed3780992e07ca29271b4a0d

Tx prefix hash: 619890c6627e2c54ebc03a7a78a8b822c2292b427ce41849f1119d6942c1070b
Tx public key: faefacd43eaa6b89bc1fa7ae7e5373ffcb3d932ac22b7f4d308055d643e81754
Timestamp: 1705291327 Timestamp [UCT]: 2024-01-15 04:02:07 Age [y:d:h:m:s]: 01:308:19:14:39
Block: 935587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479540 RingCT/type: yes/0
Extra: 01faefacd43eaa6b89bc1fa7ae7e5373ffcb3d932ac22b7f4d308055d643e817540211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12e5eeb8673a8b11a739a79dfbbf2d5e66c8e1b07a9263e1c7f1a6f6eda95e81 0.600000000000 1393603 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": 935597, "vin": [ { "gen": { "height": 935587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12e5eeb8673a8b11a739a79dfbbf2d5e66c8e1b07a9263e1c7f1a6f6eda95e81" } } ], "extra": [ 1, 250, 239, 172, 212, 62, 170, 107, 137, 188, 31, 167, 174, 126, 83, 115, 255, 203, 61, 147, 42, 194, 43, 127, 77, 48, 128, 85, 214, 67, 232, 23, 84, 2, 17, 0, 0, 0, 3, 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