Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cde0954834c9f4aeb8854ea7900b183a4de52676c476c0e5ab9b4bd033d194c0

Tx prefix hash: c417afa0bf60bb26a2a1ad131c05ed99d4afc472748f5ba635a5826c747e5e2b
Tx public key: ba7900cdda70b328df0635e8b7e51f2ec40c7aa98b251cd3767027d0d449c631
Timestamp: 1672783811 Timestamp [UCT]: 2023-01-03 22:10:11 Age [y:d:h:m:s]: 02:135:23:37:15
Block: 666963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 618911 RingCT/type: yes/0
Extra: 01ba7900cdda70b328df0635e8b7e51f2ec40c7aa98b251cd3767027d0d449c63102110000000152542ceb000000000000000000

1 output(s) for total of 3.785076602000 dcy

stealth address amount amount idx
00: b06f265e5da6d330de99f7284897883373c9172dcc3535b253a9eb34e8488b64 3.785076602000 1108122 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": 666973, "vin": [ { "gen": { "height": 666963 } } ], "vout": [ { "amount": 3785076602, "target": { "key": "b06f265e5da6d330de99f7284897883373c9172dcc3535b253a9eb34e8488b64" } } ], "extra": [ 1, 186, 121, 0, 205, 218, 112, 179, 40, 223, 6, 53, 232, 183, 229, 31, 46, 196, 12, 122, 169, 139, 37, 28, 211, 118, 112, 39, 208, 212, 73, 198, 49, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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