Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 958654c88ba9a0d09f6eb896ec0286fc407420355ceeb8aafa2d24753a79e3b3

Tx prefix hash: 86d11a29d380a6f829eba99663aa55ddabf2f0aa96678dcffa97ac6ba45bd3f6
Tx public key: 8d7a123715e25b912e4c0828b5535f5e210a4d3cb81157131c867ec279ef711b
Timestamp: 1701221756 Timestamp [UCT]: 2023-11-29 01:35:56 Age [y:d:h:m:s]: 01:133:17:30:00
Block: 901860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356749 RingCT/type: yes/0
Extra: 018d7a123715e25b912e4c0828b5535f5e210a4d3cb81157131c867ec279ef711b02110000000633af99f4000000000000000000

1 output(s) for total of 0.630613728000 dcy

stealth address amount amount idx
00: fa2bff2fdb743106bc06f3058a10a62cf942950af18c6b558363e0932d00f88a 0.630613728000 1358453 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": 901870, "vin": [ { "gen": { "height": 901860 } } ], "vout": [ { "amount": 630613728, "target": { "key": "fa2bff2fdb743106bc06f3058a10a62cf942950af18c6b558363e0932d00f88a" } } ], "extra": [ 1, 141, 122, 18, 55, 21, 226, 91, 145, 46, 76, 8, 40, 181, 83, 95, 94, 33, 10, 77, 60, 184, 17, 87, 19, 28, 134, 126, 194, 121, 239, 113, 27, 2, 17, 0, 0, 0, 6, 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