Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f27a0804286c78b7ca834b71a1c94c54fae5ea5b46d0330f9d42640a69606681

Tx prefix hash: 4613c0a6fd0803ed1346c87ac305aad661491c4e8bd357e03e6e5c7b543a3f5a
Tx public key: 4565cb68c24a08ad4d6105055ffec9cfb1ce6079b0956b1dcf2d281e92ba2253
Timestamp: 1725128253 Timestamp [UCT]: 2024-08-31 18:17:33 Age [y:d:h:m:s]: 00:221:20:20:04
Block: 1100064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158416 RingCT/type: yes/0
Extra: 014565cb68c24a08ad4d6105055ffec9cfb1ce6079b0956b1dcf2d281e92ba225302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 790cfc87d157f41c2333ee3b8fb3caa70471c06e8f377450a827ef41dd659f34 0.600000000000 1576037 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": 1100074, "vin": [ { "gen": { "height": 1100064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "790cfc87d157f41c2333ee3b8fb3caa70471c06e8f377450a827ef41dd659f34" } } ], "extra": [ 1, 69, 101, 203, 104, 194, 74, 8, 173, 77, 97, 5, 5, 95, 254, 201, 207, 177, 206, 96, 121, 176, 149, 107, 29, 207, 45, 40, 30, 146, 186, 34, 83, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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