Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1be8e9f16596e1b4b937516175d49490683321106aa2c312b5408741bd9c7a4

Tx prefix hash: 585c5c232c145672d3e7e567246e38d7454f6381f50d6869dc313e9a81b0f85c
Tx public key: 50eba4088ba1c236bdd27f1df2a743652b8877fb49208efc8bdb575fd0c38ca9
Timestamp: 1657626340 Timestamp [UCT]: 2022-07-12 11:45:40 Age [y:d:h:m:s]: 02:217:04:09:23
Block: 542149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 676321 RingCT/type: yes/0
Extra: 0150eba4088ba1c236bdd27f1df2a743652b8877fb49208efc8bdb575fd0c38ca9021100000009bf7ee4e7000000000000000000

1 output(s) for total of 9.809242024000 dcy

stealth address amount amount idx
00: c07264d45bc40532ccaedec51c19d17823d86e34cb810d73a327c8bb9eef092a 9.809242024000 972672 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": 542159, "vin": [ { "gen": { "height": 542149 } } ], "vout": [ { "amount": 9809242024, "target": { "key": "c07264d45bc40532ccaedec51c19d17823d86e34cb810d73a327c8bb9eef092a" } } ], "extra": [ 1, 80, 235, 164, 8, 139, 161, 194, 54, 189, 210, 127, 29, 242, 167, 67, 101, 43, 136, 119, 251, 73, 32, 142, 252, 139, 219, 87, 95, 208, 195, 140, 169, 2, 17, 0, 0, 0, 9, 191, 126, 228, 231, 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