Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5f3cc06ef6b23220bbea9f43fdd8c200fd065ced0aa14a350cd2730cf8f9724

Tx prefix hash: 177d39ce4cc81b34fb8dd81be8b0781b557efa8e29268aee1c9505b0136b91ce
Tx public key: 3b386d19eb2e0a5cc4457765a1cec40279596e80c2b71231aac46649bbdc4c4c
Timestamp: 1715773556 Timestamp [UCT]: 2024-05-15 11:45:56 Age [y:d:h:m:s]: 00:240:14:30:20
Block: 1022519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172193 RingCT/type: yes/0
Extra: 013b386d19eb2e0a5cc4457765a1cec40279596e80c2b71231aac46649bbdc4c4c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c98ef1ec2326fa33eb9074111835481d57856a7143726a6b4d6d87ea3fc3ce8 0.600000000000 1487146 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": 1022529, "vin": [ { "gen": { "height": 1022519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c98ef1ec2326fa33eb9074111835481d57856a7143726a6b4d6d87ea3fc3ce8" } } ], "extra": [ 1, 59, 56, 109, 25, 235, 46, 10, 92, 196, 69, 119, 101, 161, 206, 196, 2, 121, 89, 110, 128, 194, 183, 18, 49, 170, 196, 102, 73, 187, 220, 76, 76, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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