Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e81128ef14224a52c10875f3f59560b942877da71e72cae0b2aac8d869d1e66

Tx prefix hash: 6b6336ea67280845e93f03425bf2c0e180b197e4ee7e4469ae54e464f08bf85e
Tx public key: fc1cce5e321454d097703230a724ddd2f809f1f87a90fed8eb3ad774c39a88ea
Timestamp: 1703084727 Timestamp [UCT]: 2023-12-20 15:05:27 Age [y:d:h:m:s]: 01:148:19:39:04
Block: 917322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367513 RingCT/type: yes/0
Extra: 01fc1cce5e321454d097703230a724ddd2f809f1f87a90fed8eb3ad774c39a88ea021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18358ea1d53625a7ca298943f3f85b9a2b2dd70971b9f05f73c5bf2a336bc1fa 0.600000000000 1374894 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": 917332, "vin": [ { "gen": { "height": 917322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18358ea1d53625a7ca298943f3f85b9a2b2dd70971b9f05f73c5bf2a336bc1fa" } } ], "extra": [ 1, 252, 28, 206, 94, 50, 20, 84, 208, 151, 112, 50, 48, 167, 36, 221, 210, 248, 9, 241, 248, 122, 144, 254, 216, 235, 58, 215, 116, 195, 154, 136, 234, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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