Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfc49fcc581831718014d4e87203347dc5a0334c1ce3fb5fe567f0f1fea833b4

Tx prefix hash: 67292eb1195df9972979cef304243c85361e592a045d4d64818eeb3fda3d98b9
Tx public key: 20ba29a5da4b012099fee6910a62af2732d3e6e5637975e5046a35cba6fd4a35
Timestamp: 1730479636 Timestamp [UCT]: 2024-11-01 16:47:16 Age [y:d:h:m:s]: 00:167:13:23:17
Block: 1144359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119593 RingCT/type: yes/0
Extra: 0120ba29a5da4b012099fee6910a62af2732d3e6e5637975e5046a35cba6fd4a35021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab1686ad83c5f22639322c69a0855c7a8007963b5bbdd96fdd75264314b3ea03 0.600000000000 1628552 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": 1144369, "vin": [ { "gen": { "height": 1144359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab1686ad83c5f22639322c69a0855c7a8007963b5bbdd96fdd75264314b3ea03" } } ], "extra": [ 1, 32, 186, 41, 165, 218, 75, 1, 32, 153, 254, 230, 145, 10, 98, 175, 39, 50, 211, 230, 229, 99, 121, 117, 229, 4, 106, 53, 203, 166, 253, 74, 53, 2, 17, 0, 0, 0, 6, 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