Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13e783bb1e3341aea938739c434057f429a0fc511bcbf2a21a87c30587af119f

Tx prefix hash: 94b1bec31378b9e093b84e4a9d9fd8e2f7aba9801af5f93c148b8f1b8af8e05c
Tx public key: cd5c929da906f2e43f0f341032494f00165492926f0ece2120324ef3dc8e41ec
Timestamp: 1674970633 Timestamp [UCT]: 2023-01-29 05:37:13 Age [y:d:h:m:s]: 02:065:03:25:22
Block: 685113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 568185 RingCT/type: yes/0
Extra: 01cd5c929da906f2e43f0f341032494f00165492926f0ece2120324ef3dc8e41ec0211000000015029cbac000000000000000000

1 output(s) for total of 3.295612657000 dcy

stealth address amount amount idx
00: 80db15b52c399c521081395ebdfa9cc11d054de84196e40dc9fdf1f1fcc1526c 3.295612657000 1127402 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": 685123, "vin": [ { "gen": { "height": 685113 } } ], "vout": [ { "amount": 3295612657, "target": { "key": "80db15b52c399c521081395ebdfa9cc11d054de84196e40dc9fdf1f1fcc1526c" } } ], "extra": [ 1, 205, 92, 146, 157, 169, 6, 242, 228, 63, 15, 52, 16, 50, 73, 79, 0, 22, 84, 146, 146, 111, 14, 206, 33, 32, 50, 78, 243, 220, 142, 65, 236, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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