Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3443ac07bdcc74217061dfd012ca7676ddeaab680b385579a2c0ec9dcf14aa88

Tx prefix hash: bf15d1c7932e15c873f69ddd3b5983e37a0b03d3da7bc52e5e7b60c9ae41bab0
Tx public key: 5757b9e870af2e497bd848e6720e9296d837e8ae723e470a249d036d2e38d87f
Timestamp: 1695927171 Timestamp [UCT]: 2023-09-28 18:52:51 Age [y:d:h:m:s]: 01:243:09:06:46
Block: 858187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435037 RingCT/type: yes/0
Extra: 015757b9e870af2e497bd848e6720e9296d837e8ae723e470a249d036d2e38d87f021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.879974857000 dcy

stealth address amount amount idx
00: 2cd7a458ae921d2fa0b61288591135af11d9cc7b7aa7d96fdae214e5289f033f 0.879974857000 1312353 of 0

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": 858197, "vin": [ { "gen": { "height": 858187 } } ], "vout": [ { "amount": 879974857, "target": { "key": "2cd7a458ae921d2fa0b61288591135af11d9cc7b7aa7d96fdae214e5289f033f" } } ], "extra": [ 1, 87, 87, 185, 232, 112, 175, 46, 73, 123, 216, 72, 230, 114, 14, 146, 150, 216, 55, 232, 174, 114, 62, 71, 10, 36, 157, 3, 109, 46, 56, 216, 127, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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