Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7f82313a35a7385315cafba3e1e4c7683697da3a06159ffa5e0935257af62ae

Tx prefix hash: e80a663f8a6b2c6e9c65f67840aa3decbc70478bdbfa06f8374698de15867d44
Tx public key: 32a1f6c31cc96e91ea1943b6e8327262e728ba31da3698da545a23b3e19e29c7
Timestamp: 1676362929 Timestamp [UCT]: 2023-02-14 08:22:09 Age [y:d:h:m:s]: 02:011:17:04:42
Block: 696670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529922 RingCT/type: yes/0
Extra: 0132a1f6c31cc96e91ea1943b6e8327262e728ba31da3698da545a23b3e19e29c702110000000433af99f4000000000000000000

1 output(s) for total of 3.017470317000 dcy

stealth address amount amount idx
00: 16ab364e24c6534c31dc9878efcbaeb1339dc05c943485e4ec50a980274eaaac 3.017470317000 1139711 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": 696680, "vin": [ { "gen": { "height": 696670 } } ], "vout": [ { "amount": 3017470317, "target": { "key": "16ab364e24c6534c31dc9878efcbaeb1339dc05c943485e4ec50a980274eaaac" } } ], "extra": [ 1, 50, 161, 246, 195, 28, 201, 110, 145, 234, 25, 67, 182, 232, 50, 114, 98, 231, 40, 186, 49, 218, 54, 152, 218, 84, 90, 35, 179, 225, 158, 41, 199, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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