Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fa6c178d80bbf2a9342a849296f96726b0032a3c4d830ca21859f9c8f8bb6e6

Tx prefix hash: cd70464a3da4c39bc48019da643ef39929b2958183257a826334da137b64316a
Tx public key: cf69d1e2e82c480e5c49a399700bb8ff9fcecef36e831a8e40d4df07e19826c8
Timestamp: 1673855711 Timestamp [UCT]: 2023-01-16 07:55:11 Age [y:d:h:m:s]: 02:002:05:54:31
Block: 675853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523499 RingCT/type: yes/0
Extra: 01cf69d1e2e82c480e5c49a399700bb8ff9fcecef36e831a8e40d4df07e19826c80211000000028b7b6602000000000000000000

1 output(s) for total of 3.536864319000 dcy

stealth address amount amount idx
00: 05560f6e795a1d5df3d10a6df561d2e8c6015dc6c9612cad8a7dd0dcaa5efc74 3.536864319000 1117540 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": 675863, "vin": [ { "gen": { "height": 675853 } } ], "vout": [ { "amount": 3536864319, "target": { "key": "05560f6e795a1d5df3d10a6df561d2e8c6015dc6c9612cad8a7dd0dcaa5efc74" } } ], "extra": [ 1, 207, 105, 209, 226, 232, 44, 72, 14, 92, 73, 163, 153, 112, 11, 184, 255, 159, 206, 206, 243, 110, 131, 26, 142, 64, 212, 223, 7, 225, 152, 38, 200, 2, 17, 0, 0, 0, 2, 139, 123, 102, 2, 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