Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab7dc01137c699f5d2720f19fc291b341cab2f48508a4562a25c3ec04181f743

Tx prefix hash: ef67f613f5dba074898aba4d9acb15e30194325a42140111833d03b2e07ac3d9
Tx public key: 56c299086cca9d19a61d94e19c678fa5d0e21c541ce1b126b44d9c94d0a3eabf
Timestamp: 1688199642 Timestamp [UCT]: 2023-07-01 08:20:42 Age [y:d:h:m:s]: 01:241:03:23:23
Block: 794166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433464 RingCT/type: yes/0
Extra: 0156c299086cca9d19a61d94e19c678fa5d0e21c541ce1b126b44d9c94d0a3eabf021100000001faf35c9c000000000000000000

1 output(s) for total of 1.434162975000 dcy

stealth address amount amount idx
00: 294cc4a8ec10b74c3a1f7dfd6a1a7fd71f2c739a8c8cd0931bf0aacd24d5eaca 1.434162975000 1244893 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": 794176, "vin": [ { "gen": { "height": 794166 } } ], "vout": [ { "amount": 1434162975, "target": { "key": "294cc4a8ec10b74c3a1f7dfd6a1a7fd71f2c739a8c8cd0931bf0aacd24d5eaca" } } ], "extra": [ 1, 86, 194, 153, 8, 108, 202, 157, 25, 166, 29, 148, 225, 156, 103, 143, 165, 208, 226, 28, 84, 28, 225, 177, 38, 180, 77, 156, 148, 208, 163, 234, 191, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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