Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca1fc6cab6ea59063bdbd8146946cd44c2d9a1bc5aaac08b029086962ab7e69b

Tx prefix hash: bba5acbe9dcbb267334e8c765e7715facb2d7fef1e8b2e7b1512f52e5d394529
Tx public key: 8a94c509cf37262fe337c4175a404e47352ff83cddfb55f0945db91362f83b82
Timestamp: 1682794801 Timestamp [UCT]: 2023-04-29 19:00:01 Age [y:d:h:m:s]: 01:343:04:38:17
Block: 749351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506520 RingCT/type: yes/0
Extra: 018a94c509cf37262fe337c4175a404e47352ff83cddfb55f0945db91362f83b82021100000001faf35c9c000000000000000000

1 output(s) for total of 2.018781288000 dcy

stealth address amount amount idx
00: ff261b74c5ecdc1753a6041d37bf5bbd07fb728880d0c8dfdbd0d9a4ca006ef2 2.018781288000 1197306 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": 749361, "vin": [ { "gen": { "height": 749351 } } ], "vout": [ { "amount": 2018781288, "target": { "key": "ff261b74c5ecdc1753a6041d37bf5bbd07fb728880d0c8dfdbd0d9a4ca006ef2" } } ], "extra": [ 1, 138, 148, 197, 9, 207, 55, 38, 47, 227, 55, 196, 23, 90, 64, 78, 71, 53, 47, 248, 60, 221, 251, 85, 240, 148, 93, 185, 19, 98, 248, 59, 130, 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