Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f4d64c8f0717ec8051007f2090f9a4da33c0753460edb725e6364719e683ee2

Tx prefix hash: 191eac79e85f26bd3eabc41dcd5adf5cd73b76f3fb2c8835a0af51b82315cab2
Tx public key: 9c81735ec86b40a1f260eb0bc1c33c56e29ea69053fae1275c6e88f88334a9ff
Timestamp: 1725232859 Timestamp [UCT]: 2024-09-01 23:20:59 Age [y:d:h:m:s]: 00:214:11:43:29
Block: 1100941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153142 RingCT/type: yes/0
Extra: 019c81735ec86b40a1f260eb0bc1c33c56e29ea69053fae1275c6e88f88334a9ff02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d68fb44d73d0115e6559df56414e0cae377f88a23faca5e4f11aa3b6957a79e 0.600000000000 1576922 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": 1100951, "vin": [ { "gen": { "height": 1100941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d68fb44d73d0115e6559df56414e0cae377f88a23faca5e4f11aa3b6957a79e" } } ], "extra": [ 1, 156, 129, 115, 94, 200, 107, 64, 161, 242, 96, 235, 11, 193, 195, 60, 86, 226, 158, 166, 144, 83, 250, 225, 39, 92, 110, 136, 248, 131, 52, 169, 255, 2, 17, 0, 0, 0, 1, 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