Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 464fa1910c9a81b31532222fee368058b1553f41974139d911864a9fd5f99a33

Tx prefix hash: 07e16a940246c906ca07f9799dfe329af6713d418b2f453583dfe981d23ac014
Tx public key: 4de64938ca909a3d567082d165cd4a510990d7dc42baae92803b08c493695a6f
Timestamp: 1733093265 Timestamp [UCT]: 2024-12-01 22:47:45 Age [y:d:h:m:s]: 00:120:20:00:51
Block: 1166008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86147 RingCT/type: yes/0
Extra: 014de64938ca909a3d567082d165cd4a510990d7dc42baae92803b08c493695a6f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9c3e910a0074f9bef4d670a46e1e47aaf24f11106ba5a6f98abdbe9b78d2073 0.600000000000 1651685 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": 1166018, "vin": [ { "gen": { "height": 1166008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9c3e910a0074f9bef4d670a46e1e47aaf24f11106ba5a6f98abdbe9b78d2073" } } ], "extra": [ 1, 77, 230, 73, 56, 202, 144, 154, 61, 86, 112, 130, 209, 101, 205, 74, 81, 9, 144, 215, 220, 66, 186, 174, 146, 128, 59, 8, 196, 147, 105, 90, 111, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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