Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 526f3de85fa4ba68806c6ddf44ec8f9b33f659227905ca9ff532cca469341f30

Tx prefix hash: 087cbc565be30e7e48f71e19c4af284b894d52ffb9db154b3c847805bf077da8
Tx public key: a07e4ec531e97aff4ee89cd100e8596fb0ac1fd6fc132a6b2c61b879305c7a7d
Timestamp: 1674431168 Timestamp [UCT]: 2023-01-22 23:46:08 Age [y:d:h:m:s]: 02:083:22:17:10
Block: 680642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 581637 RingCT/type: yes/0
Extra: 01a07e4ec531e97aff4ee89cd100e8596fb0ac1fd6fc132a6b2c61b879305c7a7d0211000000015029cbac000000000000000000

1 output(s) for total of 3.409969132000 dcy

stealth address amount amount idx
00: f0ed7cae5f66b9cb4ad1a5ae0d050ef05486f543f596d5737408b76f1e1de396 3.409969132000 1122701 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": 680652, "vin": [ { "gen": { "height": 680642 } } ], "vout": [ { "amount": 3409969132, "target": { "key": "f0ed7cae5f66b9cb4ad1a5ae0d050ef05486f543f596d5737408b76f1e1de396" } } ], "extra": [ 1, 160, 126, 78, 197, 49, 233, 122, 255, 78, 232, 156, 209, 0, 232, 89, 111, 176, 172, 31, 214, 252, 19, 42, 107, 44, 97, 184, 121, 48, 92, 122, 125, 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