Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd1459b12a6e2fc972c3a7fcd4b3129c75336dd5e10d2cab72b87ec667c1e2c6

Tx prefix hash: 4df2cd9a5c06b0d300f7f313db7d7538630dc9901757e3f156d7d323b333a407
Tx public key: 7169c643880ddd162b460e2bb38acb35504aac40c473b041c3b4b8e386107608
Timestamp: 1661349978 Timestamp [UCT]: 2022-08-24 14:06:18 Age [y:d:h:m:s]: 02:076:03:18:22
Block: 572845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 575824 RingCT/type: yes/0
Extra: 017169c643880ddd162b460e2bb38acb35504aac40c473b041c3b4b8e38610760802110000001075e3f0e9000000000000000000

1 output(s) for total of 7.761163178000 dcy

stealth address amount amount idx
00: 31ad5f2c9f2c30221ac0c943c4bd7e39e4bdcea2432c9f11b399a769192821fd 7.761163178000 1006117 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": 572855, "vin": [ { "gen": { "height": 572845 } } ], "vout": [ { "amount": 7761163178, "target": { "key": "31ad5f2c9f2c30221ac0c943c4bd7e39e4bdcea2432c9f11b399a769192821fd" } } ], "extra": [ 1, 113, 105, 198, 67, 136, 13, 221, 22, 43, 70, 14, 43, 179, 138, 203, 53, 80, 74, 172, 64, 196, 115, 176, 65, 195, 180, 184, 227, 134, 16, 118, 8, 2, 17, 0, 0, 0, 16, 117, 227, 240, 233, 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