Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f8fb443f3a67a9b49e947f91ac0fe480c6fa4989194c48b8d661f7cb121a608

Tx prefix hash: 718e9cac57e0d583742bc57b8b453306fef6d6dd64db452bcb118fc140743882
Tx public key: 0f7f0ec9917bc7552654b61501d67c98d310890c0d8c402a0296e17bf2a4f45b
Timestamp: 1705326293 Timestamp [UCT]: 2024-01-15 13:44:53 Age [y:d:h:m:s]: 01:110:09:15:51
Block: 935883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340014 RingCT/type: yes/0
Extra: 010f7f0ec9917bc7552654b61501d67c98d310890c0d8c402a0296e17bf2a4f45b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 098e9d13a7b6fbbe81e1a989b1a957e235119f38278ff73961af1a08a2712cea 0.600000000000 1393901 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": 935893, "vin": [ { "gen": { "height": 935883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "098e9d13a7b6fbbe81e1a989b1a957e235119f38278ff73961af1a08a2712cea" } } ], "extra": [ 1, 15, 127, 14, 201, 145, 123, 199, 85, 38, 84, 182, 21, 1, 214, 124, 152, 211, 16, 137, 12, 13, 140, 64, 42, 2, 150, 225, 123, 242, 164, 244, 91, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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