Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68e46237e6f65d460ee46aa6bd2bc9c96580b61886447475ed1fd4bdfb90779

Tx prefix hash: 5af6aafaf0eeac810665e15e8929a79a00cd1365743bec9e5e35a436d4cd99bd
Tx public key: f83cb92a3f5d9d6a958dbb12f9c0826bb34cca4b000cba81890cf044449676e8
Timestamp: 1685483746 Timestamp [UCT]: 2023-05-30 21:55:46 Age [y:d:h:m:s]: 01:275:09:48:10
Block: 771652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458010 RingCT/type: yes/0
Extra: 01f83cb92a3f5d9d6a958dbb12f9c0826bb34cca4b000cba81890cf044449676e8021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.702929886000 dcy

stealth address amount amount idx
00: da5970c6956e5a2991f10c5c9ed25f3cfd8e868e6d0c9a323f02ad114024fcd1 1.702929886000 1221027 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": 771662, "vin": [ { "gen": { "height": 771652 } } ], "vout": [ { "amount": 1702929886, "target": { "key": "da5970c6956e5a2991f10c5c9ed25f3cfd8e868e6d0c9a323f02ad114024fcd1" } } ], "extra": [ 1, 248, 60, 185, 42, 63, 93, 157, 106, 149, 141, 187, 18, 249, 192, 130, 107, 179, 76, 202, 75, 0, 12, 186, 129, 137, 12, 240, 68, 68, 150, 118, 232, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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