Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fff908bd79faf8cc39d8f2c06d70f3ba2aa95fe7646e627b02d8a840c7535591

Tx prefix hash: 4c3b2af065577c557d644683d4b11398039ce563d0bc1c9422be02a6ba8db513
Tx public key: 0a14e3cc34fb05c29d7958fcfba776cc9a5b0fda10202d7feca9e50ecac77eab
Timestamp: 1699642993 Timestamp [UCT]: 2023-11-10 19:03:13 Age [y:d:h:m:s]: 01:072:15:44:54
Block: 888787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313297 RingCT/type: yes/0
Extra: 010a14e3cc34fb05c29d7958fcfba776cc9a5b0fda10202d7feca9e50ecac77eab02110000000333af99f4000000000000000000

1 output(s) for total of 0.696754393000 dcy

stealth address amount amount idx
00: 88e13a0992c516f57e1e78427a579157b61962892de4bebfd935b2f4150cc2a6 0.696754393000 1344746 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": 888797, "vin": [ { "gen": { "height": 888787 } } ], "vout": [ { "amount": 696754393, "target": { "key": "88e13a0992c516f57e1e78427a579157b61962892de4bebfd935b2f4150cc2a6" } } ], "extra": [ 1, 10, 20, 227, 204, 52, 251, 5, 194, 157, 121, 88, 252, 251, 167, 118, 204, 154, 91, 15, 218, 16, 32, 45, 127, 236, 169, 229, 14, 202, 199, 126, 171, 2, 17, 0, 0, 0, 3, 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