Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a9246a8b7ea92ed165c68071b4897d4d5e216d587d979a831c16bc5dad013c6

Tx prefix hash: 7701ff6093e51ada097961924b9e32a69caf29ccee58fdf06a350c2c51bebc14
Tx public key: a1dcef46a13e87a29a1da16e20e38ddcdea1a01fb9834fac1f450a4dc9760cbe
Timestamp: 1712179340 Timestamp [UCT]: 2024-04-03 21:22:20 Age [y:d:h:m:s]: 00:221:08:45:19
Block: 992686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158505 RingCT/type: yes/0
Extra: 01a1dcef46a13e87a29a1da16e20e38ddcdea1a01fb9834fac1f450a4dc9760cbe0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b61b308e2418977dda9b295758073ba011b448f95e2e9cc57cf17d02f617a3f4 0.600000000000 1453060 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": 992696, "vin": [ { "gen": { "height": 992686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b61b308e2418977dda9b295758073ba011b448f95e2e9cc57cf17d02f617a3f4" } } ], "extra": [ 1, 161, 220, 239, 70, 161, 62, 135, 162, 154, 29, 161, 110, 32, 227, 141, 220, 222, 161, 160, 31, 185, 131, 79, 172, 31, 69, 10, 77, 201, 118, 12, 190, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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