Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b19f20752f19a33766261db98f9eb0d61b3258fe188aad87f282c93d1ed9356a

Tx prefix hash: 0a79c5128a413ac1422f1937a668ed5cb16ce2b234cfb96b4bc2395282221c48
Tx public key: b4566ce3b67f4c099f72642b21bea1bba3d3a0ef8c9a327c299023f959cc1a6f
Timestamp: 1728658841 Timestamp [UCT]: 2024-10-11 15:00:41 Age [y:d:h:m:s]: 00:177:08:30:53
Block: 1129342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126526 RingCT/type: yes/0
Extra: 01b4566ce3b67f4c099f72642b21bea1bba3d3a0ef8c9a327c299023f959cc1a6f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f86bbea11d522736cdbe39fc88559d5237f990ca014f97b9b4c174d538a16cc5 0.600000000000 1612167 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": 1129352, "vin": [ { "gen": { "height": 1129342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f86bbea11d522736cdbe39fc88559d5237f990ca014f97b9b4c174d538a16cc5" } } ], "extra": [ 1, 180, 86, 108, 227, 182, 127, 76, 9, 159, 114, 100, 43, 33, 190, 161, 187, 163, 211, 160, 239, 140, 154, 50, 124, 41, 144, 35, 249, 89, 204, 26, 111, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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