Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba1f8b013ec30d8f2be4cebb852cdcfd518ddd654e2705c90b604eb01c0576c7

Tx prefix hash: d44d36369ddc3d29c5f9c9046e97c95bd81e961d005d859a813c3380386551d9
Tx public key: 317bc443cb82b7f8d6c83b778be92330d929ecf4e98f6242678eb040689727cb
Timestamp: 1721269268 Timestamp [UCT]: 2024-07-18 02:21:08 Age [y:d:h:m:s]: 00:273:03:31:19
Block: 1068089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195142 RingCT/type: yes/0
Extra: 01317bc443cb82b7f8d6c83b778be92330d929ecf4e98f6242678eb040689727cb02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50f6ab7691c4e659117c845e57179a532486ea878dbbbc7e9c247dcb93d612cb 0.600000000000 1539100 of 15

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": 1068099, "vin": [ { "gen": { "height": 1068089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50f6ab7691c4e659117c845e57179a532486ea878dbbbc7e9c247dcb93d612cb" } } ], "extra": [ 1, 49, 123, 196, 67, 203, 130, 183, 248, 214, 200, 59, 119, 139, 233, 35, 48, 217, 41, 236, 244, 233, 143, 98, 66, 103, 142, 176, 64, 104, 151, 39, 203, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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