Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b4fb71fc103eae59fc0d748a63904b418315af517422f260a79b60f7fbd2113

Tx prefix hash: 868682f9421fdf08c438b3a84679bd7187c8ea95e4de8964068f8371fff0d6e7
Tx public key: c34d37e0111ef873f64b5e43507c39883cdcd746bf2d2e861beea4f4bc24c054
Timestamp: 1736526206 Timestamp [UCT]: 2025-01-10 16:23:26 Age [y:d:h:m:s]: 00:312:22:10:53
Block: 1194417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221165 RingCT/type: yes/0
Extra: 01c34d37e0111ef873f64b5e43507c39883cdcd746bf2d2e861beea4f4bc24c0540211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15056b318e0c67f4bd4692bbb617a5644141f7b220a1ad7b13811e1ada978344 0.600000000000 1680988 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": 1194427, "vin": [ { "gen": { "height": 1194417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15056b318e0c67f4bd4692bbb617a5644141f7b220a1ad7b13811e1ada978344" } } ], "extra": [ 1, 195, 77, 55, 224, 17, 30, 248, 115, 246, 75, 94, 67, 80, 124, 57, 136, 60, 220, 215, 70, 191, 45, 46, 134, 27, 238, 164, 244, 188, 36, 192, 84, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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