Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc34e4b41bd681575893c37fe5d4e3b28165d63d5b1fcf62f1875584aabc1cd1

Tx prefix hash: c1b5dcfc14384928bf04539b7e6aa92eea8e696076e97baeccaf29af3b9d5738
Tx public key: b37ff74f1f82e62d5570792a21222bbe95a364dae1f8ce639b16c49a22fa95e0
Timestamp: 1730674529 Timestamp [UCT]: 2024-11-03 22:55:29 Age [y:d:h:m:s]: 00:147:06:35:41
Block: 1145967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105085 RingCT/type: yes/0
Extra: 01b37ff74f1f82e62d5570792a21222bbe95a364dae1f8ce639b16c49a22fa95e00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21e274aea71de1a213cc6b070e04a9c289813fcf985fb156486a0d3a9b8d07df 0.600000000000 1630506 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": 1145977, "vin": [ { "gen": { "height": 1145967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21e274aea71de1a213cc6b070e04a9c289813fcf985fb156486a0d3a9b8d07df" } } ], "extra": [ 1, 179, 127, 247, 79, 31, 130, 230, 45, 85, 112, 121, 42, 33, 34, 43, 190, 149, 163, 100, 218, 225, 248, 206, 99, 155, 22, 196, 154, 34, 250, 149, 224, 2, 17, 0, 0, 0, 3, 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